Update the maven snapshot publish endpoint and credential#5419
Merged
willyborankin merged 1 commit intoopensearch-project:mainfrom Jun 21, 2025
Merged
Update the maven snapshot publish endpoint and credential#5419willyborankin merged 1 commit intoopensearch-project:mainfrom
willyborankin merged 1 commit intoopensearch-project:mainfrom
Conversation
RyanL1997
previously approved these changes
Jun 20, 2025
Signed-off-by: Zelin Hao <zelinhao@amazon.com>
fcb20dd to
4da4ac9
Compare
RyanL1997
approved these changes
Jun 20, 2025
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5419 +/- ##
==========================================
- Coverage 72.42% 72.37% -0.05%
==========================================
Files 394 394
Lines 24291 24291
Branches 3713 3713
==========================================
- Hits 17592 17581 -11
- Misses 4871 4882 +11
Partials 1828 1828 🚀 New features to boost your workflow:
|
willyborankin
approved these changes
Jun 21, 2025
224eb2a
into
opensearch-project:main
70 of 73 checks passed
Member
|
Hi maintainers, Thanks! |
Contributor
|
The backport to To backport manually, run these commands in your terminal: # Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/security/backport-2.19 2.19
# Navigate to the new working tree
pushd ../.worktrees/security/backport-2.19
# Create a new branch
git switch --create backport/backport-5419-to-2.19
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 224eb2afddf2cd46cb046989a9b6a2ac9c6e8473
# Push it to GitHub
git push --set-upstream origin backport/backport-5419-to-2.19
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/security/backport-2.19Then, create a pull request where the |
DarshitChanpura
pushed a commit
to DarshitChanpura/security
that referenced
this pull request
Jul 1, 2025
…-project#5419) Signed-off-by: Zelin Hao <zelinhao@amazon.com> (cherry picked from commit 224eb2a)
5 tasks
RyanL1997
pushed a commit
that referenced
this pull request
Jul 1, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Update the Maven Snapshots publish URL in accordance with the recent Sonatype migration.
https://central.sonatype.org/publish/publish-portal-snapshots/
We have stored the
onepasswordtoken in this repo secrets and new credentials for Sonatypes username & password have been stored inonepassword. These credentials will be exported as env variables which used by maven publish.Related Issues
Part of a campaign issue opensearch-project/opensearch-build#5551
Is this a backport? If so, please add backport PR # and/or commits #, and remove
backport-failedlabel from the original PR.Do these changes introduce new permission(s) to be displayed in the static dropdown on the front-end? If so, please open a draft PR in the security dashboards plugin and link the draft PR here
Testing
[Please provide details of testing done: unit testing, integration testing and manual testing]
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.